HSEARCH-5517 Adjust index plan updates caused by "association" for deleted entities#4887
Conversation
marko-bekhta
force-pushed
the
fix/HSEARCH-5517-Document-is-updated-instead-of-deleted-on-cascading-delete-in-OneToOne-relations
branch
from
a7668c3 to
2e1f0c0
Compare
I don't think so ... if we start removing things explicitly without cascading, then ORM would force us to set nulls or we'll get Hibernate ORM exceptions about those dangling objects ... (I think we already have tests for that scenario in place)...
yeah... I only could get it to "fail" with this mapping, removing any other part of what's in was leading to a different oreder of remove events and all was "ok" in a sense that update was planned first but then the remove event from ORM came in and the final plan was correct ... 😖 |
marko-bekhta
force-pushed
the
fix/HSEARCH-5517-Document-is-updated-instead-of-deleted-on-cascading-delete-in-OneToOne-relations
branch
from
2e1f0c0 to
4ebe234
Compare
|
Hey. I see this stalled -- were you waiting for some input from me? Because I don't have much to add :) |
marko-bekhta
force-pushed
the
fix/HSEARCH-5517-Document-is-updated-instead-of-deleted-on-cascading-delete-in-OneToOne-relations
branch
from
4ebe234 to
fd318d4
Compare
|
hey 🙂 👋🏻
it was more like waiting for myself to decide. Each time I open it I think: well it seems fine but can it break some other use case ? 🫣 🙂 |
|
2 participants
https://hibernate.atlassian.net/browse/HSEARCH-5517
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license
and can be relicensed under the terms of the LGPL v2.1 license in the future at the maintainers' discretion.
For more information on licensing, please check here.